Skip to content

chore(releases): update minor version criterion#996

Open
marbens-arch wants to merge 1 commit intosyncthing:mainfrom
marbens-arch:update-minor-version-definition
Open

chore(releases): update minor version criterion#996
marbens-arch wants to merge 1 commit intosyncthing:mainfrom
marbens-arch:update-minor-version-definition

Conversation

@marbens-arch
Copy link
Member

@marbens-arch marbens-arch commented Mar 7, 2026

For some time (since syncthing/syncthing@58c85fc I think), the minor version criterion hasn't been up to date.

For instance, v2.0.16-rc.1 contains a "configuration change so that a downgrade might be problematic", but is still a patch version.

I think the version number is automatically chosen based on commit type when pushing to release or release-rc branch.

https://github.com/syncthing/syncthing/blob/8c7c413f5cc6690865e4c9b5fabbe9227b52138c/script/next-version.go#L61-L73

For some time, the minor version criterion hasn't been up to date.

For instance, v2.0.16-rc.1 contains a "configuration change so that a downgrade might be problematic",
but is still a patch version.
@acolomb
Copy link
Member

acolomb commented Mar 8, 2026

IMHO, the automation regarding version bumps from commit subjects is fine and could be documented here as well. The real problem I see is that sometimes the commits are not tagged properly, leading to a minor version not being bumped although it should have been. Semantically, I fully agree with the old definition you're removing here. In reality, that guidance wasn't always followed, but that doesn't invalidate the intention stated here in the docs.

@marbens-arch
Copy link
Member Author

marbens-arch commented Mar 10, 2026

IMHO feat implies API changes, but non-feat type does not necessarily mean no API changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants